Add logging for unsupported types present when generating to/from methods #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #84
This PR modifies the handling of code generation for
To<...>()/From<...>()
methods. Refer to #84 for details.If a spec contains an unsupported type during the generation of
To<...>()/From<...>()
methods, theTo<...>()/From<...>()
methods are not generated, and an error is raised and logged.For example, the following spec, which contains a list attribute, with an element type that is also a list:
Now results in the generation of the following log message: